Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf9925d7a722cf133846d3b2ed864ad07a32f272dfc7f2c244ffab2cc75d6758

Tx prefix hash: f691f5e24881f430db7d88b4fbe97c1c06a84ce27a040893c192898e123603f7
Tx public key: 9413c4d8f36cd14d9dd0e2065e158501e99d68c678a6c54b9b90e0824fbde33d
Timestamp: 1585040416 Timestamp [UCT]: 2020-03-24 09:00:16 Age [y:d:h:m:s]: 05:071:19:12:17
Block: 87793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209009 RingCT/type: yes/0
Extra: 019413c4d8f36cd14d9dd0e2065e158501e99d68c678a6c54b9b90e0824fbde33d0211000001e9a86a1a65000000000000000000

1 output(s) for total of 314.127620757000 dcy

stealth address amount amount idx
00: 24fadf02ebede706671cc33e91a073d665bfd26ff59e452ba58d919b2432abea 314.127620757000 158037 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": 87803, "vin": [ { "gen": { "height": 87793 } } ], "vout": [ { "amount": 314127620757, "target": { "key": "24fadf02ebede706671cc33e91a073d665bfd26ff59e452ba58d919b2432abea" } } ], "extra": [ 1, 148, 19, 196, 216, 243, 108, 209, 77, 157, 208, 226, 6, 94, 21, 133, 1, 233, 157, 104, 198, 120, 166, 197, 75, 155, 144, 224, 130, 79, 189, 227, 61, 2, 17, 0, 0, 1, 233, 168, 106, 26, 101, 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