Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1dc0425ba890d2940a90e87861d7733e36c0eac4271b2a5276ccc121237e765

Tx prefix hash: 34be5f9bc0a2dea6c34432647be01ac60198dada4d9d4aedcb452f7238ad4773
Tx public key: 8412e32f3a317842e8cab2e5c12d8a681bb6739f9b8cd5e69d3c776aeddb08e2
Timestamp: 1712356268 Timestamp [UCT]: 2024-04-05 22:31:08 Age [y:d:h:m:s]: 01:216:16:15:14
Block: 994149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413568 RingCT/type: yes/0
Extra: 018412e32f3a317842e8cab2e5c12d8a681bb6739f9b8cd5e69d3c776aeddb08e202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78d0c03b38596a12448634012d0a8fe2aeaaa12398d3f8da91c8ca489d986b26 0.600000000000 1454551 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": 994159, "vin": [ { "gen": { "height": 994149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d0c03b38596a12448634012d0a8fe2aeaaa12398d3f8da91c8ca489d986b26" } } ], "extra": [ 1, 132, 18, 227, 47, 58, 49, 120, 66, 232, 202, 178, 229, 193, 45, 138, 104, 27, 182, 115, 159, 155, 140, 213, 230, 157, 60, 119, 106, 237, 219, 8, 226, 2, 17, 0, 0, 0, 3, 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