Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ef8b8465c12c7c785b79d95315a4a1a7ef7deb2ce67cf1b671e8e978abdefc4

Tx prefix hash: 65ce2c631050bf5f915ab0815a5f2f4a98b97e1f77d39cd23cee241d3cbe35b7
Tx public key: 0fa4f043107633d46f0385c0fad33c1ccb020551e109cbd5a2cb6d637ff1f7ae
Timestamp: 1737531885 Timestamp [UCT]: 2025-01-22 07:44:45 Age [y:d:h:m:s]: 00:147:15:42:32
Block: 1202718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105253 RingCT/type: yes/0
Extra: 010fa4f043107633d46f0385c0fad33c1ccb020551e109cbd5a2cb6d637ff1f7ae0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8796bc2cb82d0c2ebffe1c40bcc7341a3de89a9c43e58f0141a6fd3a96128ce6 0.600000000000 1689383 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": 1202728, "vin": [ { "gen": { "height": 1202718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8796bc2cb82d0c2ebffe1c40bcc7341a3de89a9c43e58f0141a6fd3a96128ce6" } } ], "extra": [ 1, 15, 164, 240, 67, 16, 118, 51, 212, 111, 3, 133, 192, 250, 211, 60, 28, 203, 2, 5, 81, 225, 9, 203, 213, 162, 203, 109, 99, 127, 241, 247, 174, 2, 17, 0, 0, 0, 3, 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