Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25391e0538b2a86c383c15f4b1afda0470329edbcfa1b2617bbd117083b93b5e

Tx prefix hash: 339aa004f31c876a69f90a13576d0b5fb1b74b3ba1655d894f2b5f66ae464d73
Tx public key: 789b94a5f17e9fe0f1e2ebadcb4b95388f9a9cd0de8525a9972c92202dad194b
Timestamp: 1716686875 Timestamp [UCT]: 2024-05-26 01:27:55 Age [y:d:h:m:s]: 00:359:19:51:55
Block: 1030094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257207 RingCT/type: yes/0
Extra: 01789b94a5f17e9fe0f1e2ebadcb4b95388f9a9cd0de8525a9972c92202dad194b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d314d7189e437e7ac0bc243d6e2906eb897767d874b1926d747ac38d4d9ae3a 0.600000000000 1498347 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": 1030104, "vin": [ { "gen": { "height": 1030094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d314d7189e437e7ac0bc243d6e2906eb897767d874b1926d747ac38d4d9ae3a" } } ], "extra": [ 1, 120, 155, 148, 165, 241, 126, 159, 224, 241, 226, 235, 173, 203, 75, 149, 56, 143, 154, 156, 208, 222, 133, 37, 169, 151, 44, 146, 32, 45, 173, 25, 75, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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