Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72eff67ffab8f98131e213b2824ecb237a88bb087c7d4bd3287fd20fe4420c82

Tx prefix hash: 71d8888c0c62d98aab534c5da0c794fd1aada1b94e860f2d80360a41d3cfefef
Tx public key: 57217a714ec3dd19f1aeccde68c14f9dab8d63662cb6be085a7f45181b6a528d
Timestamp: 1580624357 Timestamp [UCT]: 2020-02-02 06:19:17 Age [y:d:h:m:s]: 05:098:00:57:22
Block: 57009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221988 RingCT/type: yes/0
Extra: 0157217a714ec3dd19f1aeccde68c14f9dab8d63662cb6be085a7f45181b6a528d021100000002391a8d0e000000000000000000

1 output(s) for total of 397.317566607000 dcy

stealth address amount amount idx
00: 8abd2d1f1df3d5b7e2a5e6ce570ba654069bc57de409e5cb35010244176d72f4 397.317566607000 105088 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": 57019, "vin": [ { "gen": { "height": 57009 } } ], "vout": [ { "amount": 397317566607, "target": { "key": "8abd2d1f1df3d5b7e2a5e6ce570ba654069bc57de409e5cb35010244176d72f4" } } ], "extra": [ 1, 87, 33, 122, 113, 78, 195, 221, 25, 241, 174, 204, 222, 104, 193, 79, 157, 171, 141, 99, 102, 44, 182, 190, 8, 90, 127, 69, 24, 27, 106, 82, 141, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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