Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6d21dfded60d93b25ef28884ce66b0bc0d8a2f755f50d9c99c1d33fa85fb55

Tx prefix hash: ef492cadfb97265f02e2e23bd6fd0e88bb28d6c11674f3ac421f9388b6d811d6
Tx public key: 0ba3c1ad42536fc4ac5408848544f618cff1227b4c592a54b3b15311190e5a0c
Timestamp: 1712068640 Timestamp [UCT]: 2024-04-02 14:37:20 Age [y:d:h:m:s]: 01:049:18:52:04
Block: 991766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296609 RingCT/type: yes/0
Extra: 010ba3c1ad42536fc4ac5408848544f618cff1227b4c592a54b3b15311190e5a0c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adfe23acbf2801defd84b15967ddc4ca2586fcf10abccc6d048d1d73a33bc53f 0.600000000000 1452102 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": 991776, "vin": [ { "gen": { "height": 991766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adfe23acbf2801defd84b15967ddc4ca2586fcf10abccc6d048d1d73a33bc53f" } } ], "extra": [ 1, 11, 163, 193, 173, 66, 83, 111, 196, 172, 84, 8, 132, 133, 68, 246, 24, 207, 241, 34, 123, 76, 89, 42, 84, 179, 177, 83, 17, 25, 14, 90, 12, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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