Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f9af2ea7cc12ea13bb70e0f8b3cab65a6148eb764a4bc64267665dbc27b21d6

Tx prefix hash: 61715e61b313315bbe8fd30d08f7e15c99a76b5cff99d49cef8d6e5d6365f146
Tx public key: f569df2ddfde82f911919191a5078afcf6fdaac539f32171f7ea1cef239e0a98
Timestamp: 1735435584 Timestamp [UCT]: 2024-12-29 01:26:24 Age [y:d:h:m:s]: 00:357:17:11:39
Block: 1185389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253226 RingCT/type: yes/0
Extra: 01f569df2ddfde82f911919191a5078afcf6fdaac539f32171f7ea1cef239e0a980211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee0a9ce31363979ea0878582e5e6e215aad0f1f9304f75952cd5513c2d84667c 0.600000000000 1671856 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": 1185399, "vin": [ { "gen": { "height": 1185389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee0a9ce31363979ea0878582e5e6e215aad0f1f9304f75952cd5513c2d84667c" } } ], "extra": [ 1, 245, 105, 223, 45, 223, 222, 130, 249, 17, 145, 145, 145, 165, 7, 138, 252, 246, 253, 170, 197, 57, 243, 33, 113, 247, 234, 28, 239, 35, 158, 10, 152, 2, 17, 0, 0, 0, 16, 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