Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3703a6b654753a7443b302e9a8ede27889dfc41ace8e305ce8f39114815544a

Tx prefix hash: 17c362e3159f341b4163c887da91ae6fbf51ad048db4adac803fd4a0ff0ef61a
Tx public key: 3a4f69a78349f5ae5bd3ba21b937ce7512f6e92176e09efd311ab0fe8d4322ca
Timestamp: 1709494379 Timestamp [UCT]: 2024-03-03 19:32:59 Age [y:d:h:m:s]: 01:044:02:18:49
Block: 970464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292522 RingCT/type: yes/0
Extra: 013a4f69a78349f5ae5bd3ba21b937ce7512f6e92176e09efd311ab0fe8d4322ca0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6337ba6e4314cb8541b69a0aec64cc569dc11861a5343211f1ae50d5e0c84b4d 0.600000000000 1430317 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": 970474, "vin": [ { "gen": { "height": 970464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6337ba6e4314cb8541b69a0aec64cc569dc11861a5343211f1ae50d5e0c84b4d" } } ], "extra": [ 1, 58, 79, 105, 167, 131, 73, 245, 174, 91, 211, 186, 33, 185, 55, 206, 117, 18, 246, 233, 33, 118, 224, 158, 253, 49, 26, 176, 254, 141, 67, 34, 202, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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