Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7250397bdbe719db7f44f0911df7a7cba87438e2d8fac8784c9caf8abc66fbf

Tx prefix hash: e9e6978fc47e154809318ab2ae7db839df946ca7d940cc8489fa4dc8a4424c6e
Tx public key: a4b4e5f7bea3a27b831e0fabad369bc00f6dbca1d4a91836414841df20c02fad
Timestamp: 1741256701 Timestamp [UCT]: 2025-03-06 10:25:01 Age [y:d:h:m:s]: 00:008:05:28:31
Block: 1233330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5900 RingCT/type: yes/0
Extra: 01a4b4e5f7bea3a27b831e0fabad369bc00f6dbca1d4a91836414841df20c02fad021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8002c6ced36994e00367b10ac2d039e040a61ddf92795f8fe44a0cffbb5ddaed 0.600000000000 1720249 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": 1233340, "vin": [ { "gen": { "height": 1233330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8002c6ced36994e00367b10ac2d039e040a61ddf92795f8fe44a0cffbb5ddaed" } } ], "extra": [ 1, 164, 180, 229, 247, 190, 163, 162, 123, 131, 30, 15, 171, 173, 54, 155, 192, 15, 109, 188, 161, 212, 169, 24, 54, 65, 72, 65, 223, 32, 192, 47, 173, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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