Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e2009a70ad15e8afdce70d02bd5671dcb0de8e1ce616358c8b46bc4feab847

Tx prefix hash: e0e086c02a0201348a6eca8ad66f03d47ad9bca47ee1ea2ba1536c44c18a54ae
Tx public key: 46b4c5f4e283a1e9dcf5cbec3b77171227ff1308d7ef67978fc233e08983f212
Timestamp: 1706818259 Timestamp [UCT]: 2024-02-01 20:10:59 Age [y:d:h:m:s]: 01:063:15:41:10
Block: 948261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306568 RingCT/type: yes/0
Extra: 0146b4c5f4e283a1e9dcf5cbec3b77171227ff1308d7ef67978fc233e08983f21202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1579cc351c652cdeca8ba9839f982aa95201377f7207026c417f97c8f77f5bff 0.600000000000 1406635 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": 948271, "vin": [ { "gen": { "height": 948261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1579cc351c652cdeca8ba9839f982aa95201377f7207026c417f97c8f77f5bff" } } ], "extra": [ 1, 70, 180, 197, 244, 226, 131, 161, 233, 220, 245, 203, 236, 59, 119, 23, 18, 39, 255, 19, 8, 215, 239, 103, 151, 143, 194, 51, 224, 137, 131, 242, 18, 2, 17, 0, 0, 0, 1, 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