Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4694f652f9a7fd875fed7685b2d15b30d9c250129d88fbb3ab4cd2624dfa3188

Tx prefix hash: c486efd5640a669bb9d1d145b2bf9cdbd1416feaa962cade750f033ab6cd46c2
Tx public key: 5e96f743648d1d762e1d11a1a00bf647a0e9b16cf8d0b3486f063ce225137049
Timestamp: 1717890375 Timestamp [UCT]: 2024-06-08 23:46:15 Age [y:d:h:m:s]: 00:263:14:16:56
Block: 1040067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188343 RingCT/type: yes/0
Extra: 015e96f743648d1d762e1d11a1a00bf647a0e9b16cf8d0b3486f063ce2251370490211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a93c235651bd4356d5b150a61651d8714fe0d922d05b026f2dc0ee9d609a8fa 0.600000000000 1508722 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": 1040077, "vin": [ { "gen": { "height": 1040067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a93c235651bd4356d5b150a61651d8714fe0d922d05b026f2dc0ee9d609a8fa" } } ], "extra": [ 1, 94, 150, 247, 67, 100, 141, 29, 118, 46, 29, 17, 161, 160, 11, 246, 71, 160, 233, 177, 108, 248, 208, 179, 72, 111, 6, 60, 226, 37, 19, 112, 73, 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