Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cfed6fc56ac711157649e4fbf82844c3d83cf3ab50756c4d46c0051d10b8cb9

Tx prefix hash: 5d6a237649e26331da034f58a2e667eba6d7e1932bd8575ed262832b44c57b43
Tx public key: 064438b4f55e2894ffd4992d704347defb22f26dfea0287c5a81370fbabae6fb
Timestamp: 1697071298 Timestamp [UCT]: 2023-10-12 00:41:38 Age [y:d:h:m:s]: 01:179:00:31:28
Block: 867675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388958 RingCT/type: yes/0
Extra: 01064438b4f55e2894ffd4992d704347defb22f26dfea0287c5a81370fbabae6fb021100000002e08532b6000000000000000000

1 output(s) for total of 0.818526165000 dcy

stealth address amount amount idx
00: 0ef16daefd749ae97f05add996271e750cc5f57f987c508caa599251ce19a18d 0.818526165000 1322381 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": 867685, "vin": [ { "gen": { "height": 867675 } } ], "vout": [ { "amount": 818526165, "target": { "key": "0ef16daefd749ae97f05add996271e750cc5f57f987c508caa599251ce19a18d" } } ], "extra": [ 1, 6, 68, 56, 180, 245, 94, 40, 148, 255, 212, 153, 45, 112, 67, 71, 222, 251, 34, 242, 109, 254, 160, 40, 124, 90, 129, 55, 15, 186, 186, 230, 251, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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