Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9cbbe6a67effb55d01c9536397c5e1cb6ad301335889e8b6d6c0c5b1dd10f6

Tx prefix hash: 408e1d3f76b161cd19caec0ed7f83671d0dde59ee1d29c31a9232472e9882a17
Tx public key: 6dc1ada8ce08441d7647fe23bec7812a7e785d549750b89f3fcf0d8041ddaf4b
Timestamp: 1700639186 Timestamp [UCT]: 2023-11-22 07:46:26 Age [y:d:h:m:s]: 01:071:02:48:58
Block: 897038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311976 RingCT/type: yes/0
Extra: 016dc1ada8ce08441d7647fe23bec7812a7e785d549750b89f3fcf0d8041ddaf4b02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.654245457000 dcy

stealth address amount amount idx
00: e64c79f9a6051d51572ed70a516229793570ffba8de598b8d7bd64ab0410b5e9 0.654245457000 1353391 of 0

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": 897048, "vin": [ { "gen": { "height": 897038 } } ], "vout": [ { "amount": 654245457, "target": { "key": "e64c79f9a6051d51572ed70a516229793570ffba8de598b8d7bd64ab0410b5e9" } } ], "extra": [ 1, 109, 193, 173, 168, 206, 8, 68, 29, 118, 71, 254, 35, 190, 199, 129, 42, 126, 120, 93, 84, 151, 80, 184, 159, 63, 207, 13, 128, 65, 221, 175, 75, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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