Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d1d093ea6081a9bfc678f08cd3c803d96613c666106de6070660d2ce73a8a5

Tx prefix hash: f155ce0ce3fd1a4cb86bf613ed42ad6e2dce04b0de35296a5388dec53528e8a1
Tx public key: 965fe674d741bd418fb9908de5ddb5f44b7dad7f365a9586a72b8e7142ac814a
Timestamp: 1736901838 Timestamp [UCT]: 2025-01-15 00:43:58 Age [y:d:h:m:s]: 00:303:08:08:28
Block: 1197533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214307 RingCT/type: yes/0
Extra: 01965fe674d741bd418fb9908de5ddb5f44b7dad7f365a9586a72b8e7142ac814a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e260e3ef327884c2d2a4bebb013d000943f0cbe4fec6763b2aa8959849283b75 0.600000000000 1684144 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": 1197543, "vin": [ { "gen": { "height": 1197533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e260e3ef327884c2d2a4bebb013d000943f0cbe4fec6763b2aa8959849283b75" } } ], "extra": [ 1, 150, 95, 230, 116, 215, 65, 189, 65, 143, 185, 144, 141, 229, 221, 181, 244, 75, 125, 173, 127, 54, 90, 149, 134, 167, 43, 142, 113, 66, 172, 129, 74, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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