Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395db8625c6be97f434ff29385f307f0a8cd2b952a50cbee6bdf290f24d76925

Tx prefix hash: 643d146408bbe20ecef86879afb57313fc3f10d26f706e25a299bb4cbb1c4655
Tx public key: ee0ff6cb5887022662efe1388c48e73029092e8baf465c14288279e1f9da533b
Timestamp: 1608683425 Timestamp [UCT]: 2020-12-23 00:30:25 Age [y:d:h:m:s]: 03:344:22:05:21
Block: 167409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 998591 RingCT/type: yes/0
Extra: 01ee0ff6cb5887022662efe1388c48e73029092e8baf465c14288279e1f9da533b0211000000c24ea414e5000000000000000000

1 output(s) for total of 171.121728267000 dcy

stealth address amount amount idx
00: bb94bce790b351490c6f2c8a32bbacb362ad736a4dd41d98d164c7b4390df8b8 171.121728267000 308652 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": 167419, "vin": [ { "gen": { "height": 167409 } } ], "vout": [ { "amount": 171121728267, "target": { "key": "bb94bce790b351490c6f2c8a32bbacb362ad736a4dd41d98d164c7b4390df8b8" } } ], "extra": [ 1, 238, 15, 246, 203, 88, 135, 2, 38, 98, 239, 225, 56, 140, 72, 231, 48, 41, 9, 46, 139, 175, 70, 92, 20, 40, 130, 121, 225, 249, 218, 83, 59, 2, 17, 0, 0, 0, 194, 78, 164, 20, 229, 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