Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a900d126a346e872e358dfd084dbc3d60b69d25028a4666b4bf3cae7a6c37fbb

Tx prefix hash: 3da0713f020d0196624b9584beadab20089fce8271c09bc2caa97bb25bace588
Tx public key: ae0b22d0778f0e83fe42f0d0c9964330c3b411e497a8c1d912ca61ca6f62b45e
Timestamp: 1706555044 Timestamp [UCT]: 2024-01-29 19:04:04 Age [y:d:h:m:s]: 01:075:22:17:37
Block: 946071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315353 RingCT/type: yes/0
Extra: 01ae0b22d0778f0e83fe42f0d0c9964330c3b411e497a8c1d912ca61ca6f62b45e02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca776a01d6fc88006364d269854d57fdfa7434b6adefb83c8dab7be2742f4978 0.600000000000 1404401 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": 946081, "vin": [ { "gen": { "height": 946071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca776a01d6fc88006364d269854d57fdfa7434b6adefb83c8dab7be2742f4978" } } ], "extra": [ 1, 174, 11, 34, 208, 119, 143, 14, 131, 254, 66, 240, 208, 201, 150, 67, 48, 195, 180, 17, 228, 151, 168, 193, 217, 18, 202, 97, 202, 111, 98, 180, 94, 2, 17, 0, 0, 0, 14, 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