Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c697cf8fab674423c85aed58d0cbb8e51ddd3b9324779cd3e03234dc49ce2bd

Tx prefix hash: ce2d04f40772f546e3d15d1a2a94b9b9f4ecaa930ce9cedc42b49326b7190504
Tx public key: 264d9a6baef60f868536eee5342392742f9e9015bc22a039a36a8ef85408a719
Timestamp: 1577146627 Timestamp [UCT]: 2019-12-24 00:17:07 Age [y:d:h:m:s]: 05:044:02:23:52
Block: 30213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181415 RingCT/type: yes/0
Extra: 01264d9a6baef60f868536eee5342392742f9e9015bc22a039a36a8ef85408a719021100000010c3a1a09f000000000000000000

1 output(s) for total of 487.407997558000 dcy

stealth address amount amount idx
00: 5a00a00e30a2482fede6cad9e753bdb306dd86a5b52bbef95a825719491d261e 487.407997558000 49891 of 0

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": 30223, "vin": [ { "gen": { "height": 30213 } } ], "vout": [ { "amount": 487407997558, "target": { "key": "5a00a00e30a2482fede6cad9e753bdb306dd86a5b52bbef95a825719491d261e" } } ], "extra": [ 1, 38, 77, 154, 107, 174, 246, 15, 134, 133, 54, 238, 229, 52, 35, 146, 116, 47, 158, 144, 21, 188, 34, 160, 57, 163, 106, 142, 248, 84, 8, 167, 25, 2, 17, 0, 0, 0, 16, 195, 161, 160, 159, 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