Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8fe7078b99ecac27f26b864db60b33ffb45c123162dc1f12e146f3a46845cb0

Tx prefix hash: 51a3f38906e7712591f8c360a869a163f74bcf81c03d6defaf354f1003407e0a
Tx public key: 2efbbf7257f974abf33b77c19edc3edc63b326a4aaea4bec26cfec7e6059c564
Timestamp: 1734518369 Timestamp [UCT]: 2024-12-18 10:39:29 Age [y:d:h:m:s]: 00:128:06:44:30
Block: 1177834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91459 RingCT/type: yes/0
Extra: 012efbbf7257f974abf33b77c19edc3edc63b326a4aaea4bec26cfec7e6059c5640211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0380226e013daade13ed005efdd857209736c9f1e896fd7aa800362c0df770e 0.600000000000 1664211 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": 1177844, "vin": [ { "gen": { "height": 1177834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0380226e013daade13ed005efdd857209736c9f1e896fd7aa800362c0df770e" } } ], "extra": [ 1, 46, 251, 191, 114, 87, 249, 116, 171, 243, 59, 119, 193, 158, 220, 62, 220, 99, 179, 38, 164, 170, 234, 75, 236, 38, 207, 236, 126, 96, 89, 197, 100, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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