Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512d5bb75e12e615318107c5291cb2b63b34222dd01265d4c4f6097f327c013a

Tx prefix hash: 27f19ce1c1f2238aeb5355c9ea5d157e2d838e9d7d4b63f4bb0d7880e5c9ce88
Tx public key: 2cc4ba7d70a74d2fe5a909ed60dfad73c52f7f819aa75b66ea1837442fb40444
Timestamp: 1703960621 Timestamp [UCT]: 2023-12-30 18:23:41 Age [y:d:h:m:s]: 01:082:12:08:30
Block: 924571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320082 RingCT/type: yes/0
Extra: 012cc4ba7d70a74d2fe5a909ed60dfad73c52f7f819aa75b66ea1837442fb40444021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9afb9e4a5fbaf9add37a16921110918e86507763d1e3b1864b455f6a639b34f 0.600000000000 1382325 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": 924581, "vin": [ { "gen": { "height": 924571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9afb9e4a5fbaf9add37a16921110918e86507763d1e3b1864b455f6a639b34f" } } ], "extra": [ 1, 44, 196, 186, 125, 112, 167, 77, 47, 229, 169, 9, 237, 96, 223, 173, 115, 197, 47, 127, 129, 154, 167, 91, 102, 234, 24, 55, 68, 47, 180, 4, 68, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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