Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62f59c8eaf8c4679989733d4305721703371fd8a2fd5c8f734d37e7069e9319

Tx prefix hash: c3c9565e3d357b58d945dcf27ce69ae262e2ca2ee42d7a999598a13fa306f007
Tx public key: c2330b3faf5396dc5a1df33f65c655afe8bf17d2a2ee84de113b3811bfa95a10
Timestamp: 1577820707 Timestamp [UCT]: 2019-12-31 19:31:47 Age [y:d:h:m:s]: 04:331:03:03:40
Block: 35966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125738 RingCT/type: yes/0
Extra: 01c2330b3faf5396dc5a1df33f65c655afe8bf17d2a2ee84de113b3811bfa95a1002110000002f398c17aa000000000000000000

1 output(s) for total of 466.477354404000 dcy

stealth address amount amount idx
00: 1ed867da849f48b37135230f48ad00e1a19e4b5d421e4118d9739fa6ce3efb78 466.477354404000 60763 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": 35976, "vin": [ { "gen": { "height": 35966 } } ], "vout": [ { "amount": 466477354404, "target": { "key": "1ed867da849f48b37135230f48ad00e1a19e4b5d421e4118d9739fa6ce3efb78" } } ], "extra": [ 1, 194, 51, 11, 63, 175, 83, 150, 220, 90, 29, 243, 63, 101, 198, 85, 175, 232, 191, 23, 210, 162, 238, 132, 222, 17, 59, 56, 17, 191, 169, 90, 16, 2, 17, 0, 0, 0, 47, 57, 140, 23, 170, 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