Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476723277179e203ccb67f08e52435058d16c017587a3403af6a21afc2db24c3

Tx prefix hash: ce0abb2d1d7a302c21db829e36402474a9db07323e1b6a0ca4bb064083ed10e0
Tx public key: 9b96e1ba33bd990b608ddccc8d37f3129dea5be341dd62d4ddfeee81cab928b9
Timestamp: 1578290087 Timestamp [UCT]: 2020-01-06 05:54:47 Age [y:d:h:m:s]: 05:032:10:53:38
Block: 39593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173175 RingCT/type: yes/0
Extra: 019b96e1ba33bd990b608ddccc8d37f3129dea5be341dd62d4ddfeee81cab928b90211000000174943cd9f000000000000000000

1 output(s) for total of 453.745993583000 dcy

stealth address amount amount idx
00: efd4bcaebd7bfe0aa21e23b9ef4bd713dd518db7f92ab972b4d6950054b0070f 453.745993583000 68558 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": 39603, "vin": [ { "gen": { "height": 39593 } } ], "vout": [ { "amount": 453745993583, "target": { "key": "efd4bcaebd7bfe0aa21e23b9ef4bd713dd518db7f92ab972b4d6950054b0070f" } } ], "extra": [ 1, 155, 150, 225, 186, 51, 189, 153, 11, 96, 141, 220, 204, 141, 55, 243, 18, 157, 234, 91, 227, 65, 221, 98, 212, 221, 254, 238, 129, 202, 185, 40, 185, 2, 17, 0, 0, 0, 23, 73, 67, 205, 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