Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a5e0a0168f6c0af74c17a4cf4b59807015655f052a6cb47c39fe05d90adc41

Tx prefix hash: 738548a76717a915d0c1245d161e54bbf28ecdb7492f325b8b3c51faa25ae914
Tx public key: f9ad93cb4268a42ca5d3ccbcf6949ebf240eeb39003fbea8851f594acfd743a9
Timestamp: 1695184593 Timestamp [UCT]: 2023-09-20 04:36:33 Age [y:d:h:m:s]: 01:216:04:00:04
Block: 852011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415586 RingCT/type: yes/0
Extra: 01f9ad93cb4268a42ca5d3ccbcf6949ebf240eeb39003fbea8851f594acfd743a902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.922431073000 dcy

stealth address amount amount idx
00: b68fe460898a327f4a8efe30d60de9ca3905165a988cbbef9bc10033a735eef8 0.922431073000 1305825 of 0

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": 852021, "vin": [ { "gen": { "height": 852011 } } ], "vout": [ { "amount": 922431073, "target": { "key": "b68fe460898a327f4a8efe30d60de9ca3905165a988cbbef9bc10033a735eef8" } } ], "extra": [ 1, 249, 173, 147, 203, 66, 104, 164, 44, 165, 211, 204, 188, 246, 148, 158, 191, 36, 14, 235, 57, 0, 63, 190, 168, 133, 31, 89, 74, 207, 215, 67, 169, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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