Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ebcd381264d4295b34f4928b68413751076ddfafec08d1138ee12eefd7d49f1

Tx prefix hash: 76bf91176b813bb4e73996876f65786564341d866044a899d2df19f16cd0fc32
Tx public key: 9570aed0e3c6ecd3c0b6960f4e18f9ea8d891ceffaf812708d4a6eda35e7e8cc
Timestamp: 1716596098 Timestamp [UCT]: 2024-05-25 00:14:58 Age [y:d:h:m:s]: 00:276:04:45:00
Block: 1029344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197363 RingCT/type: yes/0
Extra: 019570aed0e3c6ecd3c0b6960f4e18f9ea8d891ceffaf812708d4a6eda35e7e8cc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2623e04b5d35a137446b0125aa813c97e1b0bf187886d292cb1a94bed547e8ed 0.600000000000 1497411 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": 1029354, "vin": [ { "gen": { "height": 1029344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2623e04b5d35a137446b0125aa813c97e1b0bf187886d292cb1a94bed547e8ed" } } ], "extra": [ 1, 149, 112, 174, 208, 227, 198, 236, 211, 192, 182, 150, 15, 78, 24, 249, 234, 141, 137, 28, 239, 250, 248, 18, 112, 141, 74, 110, 218, 53, 231, 232, 204, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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