Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b4e8f12169446944bd97f476ec697f6c04b175f8c24f0c0b742a7960c6a81da

Tx prefix hash: 32184d1835ffaf58d8a440de6055d2777c6d16e35ab5fe3c7824d77ad70a0f3a
Tx public key: 87922be535d3b10d9959f49f3fabfa64d8f369d05c517caf54269c4a9f3b2489
Timestamp: 1719315106 Timestamp [UCT]: 2024-06-25 11:31:46 Age [y:d:h:m:s]: 00:352:02:52:05
Block: 1051866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251641 RingCT/type: yes/0
Extra: 0187922be535d3b10d9959f49f3fabfa64d8f369d05c517caf54269c4a9f3b248902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e47a4710cbafdc51ce0511388e30fb76689139bc18ee496f6c6e0bf2d60cce4 0.600000000000 1522185 of 15

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": 1051876, "vin": [ { "gen": { "height": 1051866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e47a4710cbafdc51ce0511388e30fb76689139bc18ee496f6c6e0bf2d60cce4" } } ], "extra": [ 1, 135, 146, 43, 229, 53, 211, 177, 13, 153, 89, 244, 159, 63, 171, 250, 100, 216, 243, 105, 208, 92, 81, 124, 175, 84, 38, 156, 74, 159, 59, 36, 137, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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