Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28b40770b68b659732e4bfd7a354b0613dfdacd910ca873554270c43fdfcbcd2

Tx prefix hash: 5c30603ad64d08d664ca3469483a358fdf13c17fd5903d7209cb3c027fd5cece
Tx public key: 05c4109927a208c29febe3dbf8f02209161cf6f5fce0a8e587765b938dd1b38d
Timestamp: 1740536367 Timestamp [UCT]: 2025-02-26 02:19:27 Age [y:d:h:m:s]: 00:334:17:28:03
Block: 1227346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236904 RingCT/type: yes/0
Extra: 0105c4109927a208c29febe3dbf8f02209161cf6f5fce0a8e587765b938dd1b38d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32778f5f9a45d459f335b7305b31634b9dc84cb1b6f433de9dfec2917dbc7794 0.600000000000 1714219 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": 1227356, "vin": [ { "gen": { "height": 1227346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32778f5f9a45d459f335b7305b31634b9dc84cb1b6f433de9dfec2917dbc7794" } } ], "extra": [ 1, 5, 196, 16, 153, 39, 162, 8, 194, 159, 235, 227, 219, 248, 240, 34, 9, 22, 28, 246, 245, 252, 224, 168, 229, 135, 118, 91, 147, 141, 209, 179, 141, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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