Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f0312f48784ef010ade83eb615bdd6cf8317482ad7842397a6fd24257ffeae

Tx prefix hash: cc7103674e169c97a0b448c7f73475e4d2d2066739f58dd2d775300b1f3111fe
Tx public key: 536c2d6d61ef264cb8bf9920e68f07a6e61e22d6332ceca840dd1adea3ea8899
Timestamp: 1639476467 Timestamp [UCT]: 2021-12-14 10:07:47 Age [y:d:h:m:s]: 03:027:17:31:30
Block: 395264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798776 RingCT/type: yes/0
Extra: 01536c2d6d61ef264cb8bf9920e68f07a6e61e22d6332ceca840dd1adea3ea8899021100000003eaa12622000000000000000000

1 output(s) for total of 30.083381033000 dcy

stealth address amount amount idx
00: 1eafd249d7576ce9c64aa193ce0b1140337a8472bd0044316797e3c908b5a519 30.083381033000 793121 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": 395274, "vin": [ { "gen": { "height": 395264 } } ], "vout": [ { "amount": 30083381033, "target": { "key": "1eafd249d7576ce9c64aa193ce0b1140337a8472bd0044316797e3c908b5a519" } } ], "extra": [ 1, 83, 108, 45, 109, 97, 239, 38, 76, 184, 191, 153, 32, 230, 143, 7, 166, 230, 30, 34, 214, 51, 44, 236, 168, 64, 221, 26, 222, 163, 234, 136, 153, 2, 17, 0, 0, 0, 3, 234, 161, 38, 34, 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