Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df1595367635c2f7af1c7590bb96d6b1994f80ad60ab1a5926a39b1d388025a

Tx prefix hash: dfdb8e7a80efc1122c8e644efce9dd363ccd64b133b7723ab21e8cccd619cb64
Tx public key: 1f177bd0e505f46bf69d84c408e41fa8d2cdedc9170eaf23a7b1c19e2225bf2e
Timestamp: 1727596099 Timestamp [UCT]: 2024-09-29 07:48:19 Age [y:d:h:m:s]: 00:180:17:50:45
Block: 1120538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128971 RingCT/type: yes/0
Extra: 011f177bd0e505f46bf69d84c408e41fa8d2cdedc9170eaf23a7b1c19e2225bf2e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd59ae4a256099857da244b5f5052ae8b18f95571da62e43579e005810bd5588 0.600000000000 1602489 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": 1120548, "vin": [ { "gen": { "height": 1120538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd59ae4a256099857da244b5f5052ae8b18f95571da62e43579e005810bd5588" } } ], "extra": [ 1, 31, 23, 123, 208, 229, 5, 244, 107, 246, 157, 132, 196, 8, 228, 31, 168, 210, 205, 237, 201, 23, 14, 175, 35, 167, 177, 193, 158, 34, 37, 191, 46, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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