Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f51fe4d1ee95bf718b2ca08ab42b2ff4c0579c8453f51b1a094b23427f6869e

Tx prefix hash: b074fa6dcb5933b6f0846cec9d78bd13e26f8d12daf149241760ac1f9c789893
Tx public key: d95ac32a379b9ae490cc2379966be421f277d9d28edd48a1a2c65fdc71b164e9
Timestamp: 1710422529 Timestamp [UCT]: 2024-03-14 13:22:09 Age [y:d:h:m:s]: 01:239:13:34:27
Block: 978171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429903 RingCT/type: yes/0
Extra: 01d95ac32a379b9ae490cc2379966be421f277d9d28edd48a1a2c65fdc71b164e902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f63f79861bc409b636cea283f2d25ef367e34402855912ac81a817b7cf0119 0.600000000000 1438188 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": 978181, "vin": [ { "gen": { "height": 978171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f63f79861bc409b636cea283f2d25ef367e34402855912ac81a817b7cf0119" } } ], "extra": [ 1, 217, 90, 195, 42, 55, 155, 154, 228, 144, 204, 35, 121, 150, 107, 228, 33, 242, 119, 217, 210, 142, 221, 72, 161, 162, 198, 95, 220, 113, 177, 100, 233, 2, 17, 0, 0, 0, 4, 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