Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bfc06b7df2af635dca483887438fb2e9459191a558cf0b65b5a20b71025f23a

Tx prefix hash: 5e4019d8b82628d59f5b6f250580973b90e56ff3ccea8f87d6f2a3f382230ff8
Tx public key: dac5ecdbfcbe958e024ba4bca7e70f6da02ddb5403c9521ffa63aeaabb6d0b42
Timestamp: 1745464526 Timestamp [UCT]: 2025-04-24 03:15:26 Age [y:d:h:m:s]: 00:279:19:50:02
Block: 1268155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197630 RingCT/type: yes/0
Extra: 01dac5ecdbfcbe958e024ba4bca7e70f6da02ddb5403c9521ffa63aeaabb6d0b42021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7285121c6940daffd1785ffa4ea5f77d2499cfd066a0791d1591afd2024025a9 0.600000000000 1755384 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": 1268165, "vin": [ { "gen": { "height": 1268155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7285121c6940daffd1785ffa4ea5f77d2499cfd066a0791d1591afd2024025a9" } } ], "extra": [ 1, 218, 197, 236, 219, 252, 190, 149, 142, 2, 75, 164, 188, 167, 231, 15, 109, 160, 45, 219, 84, 3, 201, 82, 31, 250, 99, 174, 170, 187, 109, 11, 66, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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