Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae272d93edc2b1f723a59d9a760bed3bc3847dcb47417b6df9df40a9d184465a

Tx prefix hash: a5237907d26116f542d1f38f20b6997c3dc81cb5897035169b6594ae188adca7
Tx public key: b297b329c9a252d6aa069eb64a0a6ce911f22ac24670d9fdfb68a40c70c41092
Timestamp: 1713915051 Timestamp [UCT]: 2024-04-23 23:30:51 Age [y:d:h:m:s]: 00:329:11:34:59
Block: 1007116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235546 RingCT/type: yes/0
Extra: 01b297b329c9a252d6aa069eb64a0a6ce911f22ac24670d9fdfb68a40c70c410920211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92e066bdd1bc7e314a5251733a41fdb83cef0d0ff7186331bc4fb5f9b55e16e7 0.600000000000 1468354 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": 1007126, "vin": [ { "gen": { "height": 1007116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e066bdd1bc7e314a5251733a41fdb83cef0d0ff7186331bc4fb5f9b55e16e7" } } ], "extra": [ 1, 178, 151, 179, 41, 201, 162, 82, 214, 170, 6, 158, 182, 74, 10, 108, 233, 17, 242, 42, 194, 70, 112, 217, 253, 251, 104, 164, 12, 112, 196, 16, 146, 2, 17, 0, 0, 0, 5, 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