Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ce57e7895b3c12afb18db9a5789951529d5f3ee924282c17387e8e8fe19c14ab

Tx prefix hash: e6a628a4231d58bdb8da4312a0689462beef499d8cdafcfc9cb51bb76a16bdf6
Tx public key: 7c331fd167647d6092c43cb28b621fc00178301f03a28458d8013e4aa73352cc
Timestamp: 1709913435 Timestamp [UCT]: 2024-03-08 15:57:15 Age [y:d:h:m:s]: 01:078:03:52:29
Block: 973936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316896 RingCT/type: yes/0
Extra: 017c331fd167647d6092c43cb28b621fc00178301f03a28458d8013e4aa73352cc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb85e8e6eac70c3d615b5eb182d3d08228750416ff37bb092f71f5ae9aac12ea 0.600000000000 1433879 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 973946, "vin": [ { "gen": { "height": 973936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb85e8e6eac70c3d615b5eb182d3d08228750416ff37bb092f71f5ae9aac12ea" } } ], "extra": [ 1, 124, 51, 31, 209, 103, 100, 125, 96, 146, 196, 60, 178, 139, 98, 31, 192, 1, 120, 48, 31, 3, 162, 132, 88, 216, 1, 62, 74, 167, 51, 82, 204, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8