Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad2705dca3f1a102d0522468841755b0cd10da6303bf85542e0811b81a29a4c

Tx prefix hash: 6ab1a89e9de9b1289324ea8b8efb6dfc2467ae1d779e98afd64e9009d416c615
Tx public key: d804b82f406544a1179c93aa90dc2aaa11f726c226f5ca2d02c4686613fadef9
Timestamp: 1718948317 Timestamp [UCT]: 2024-06-21 05:38:37 Age [y:d:h:m:s]: 00:277:14:24:07
Block: 1048847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198342 RingCT/type: yes/0
Extra: 01d804b82f406544a1179c93aa90dc2aaa11f726c226f5ca2d02c4686613fadef90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0d580fe6dab35becba463c2b1c4cb296725ca0d7c754b70972a4af74ee4362 0.600000000000 1518934 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": 1048857, "vin": [ { "gen": { "height": 1048847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0d580fe6dab35becba463c2b1c4cb296725ca0d7c754b70972a4af74ee4362" } } ], "extra": [ 1, 216, 4, 184, 47, 64, 101, 68, 161, 23, 156, 147, 170, 144, 220, 42, 170, 17, 247, 38, 194, 38, 245, 202, 45, 2, 196, 104, 102, 19, 250, 222, 249, 2, 17, 0, 0, 0, 2, 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