Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5fa406dc66166a694018d4512fe5d5d3fbf944e6c62ed2eae60903e2112c97e

Tx prefix hash: 3c3dfaf5d4418571205e21b05b5a8982caa535eca961c0a1c1802b7cd7a39ee1
Tx public key: a26701e32916b11b06837ebb6cbedae742bd0d7cdf60a79fbfcbe37b090047a6
Timestamp: 1712907272 Timestamp [UCT]: 2024-04-12 07:34:32 Age [y:d:h:m:s]: 00:355:11:33:48
Block: 998735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254154 RingCT/type: yes/0
Extra: 01a26701e32916b11b06837ebb6cbedae742bd0d7cdf60a79fbfcbe37b090047a602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 666184a76d3df825261e76905ee81a1a9133026da662ff7d267d1c9fd7f2bfe3 0.600000000000 1459187 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": 998745, "vin": [ { "gen": { "height": 998735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "666184a76d3df825261e76905ee81a1a9133026da662ff7d267d1c9fd7f2bfe3" } } ], "extra": [ 1, 162, 103, 1, 227, 41, 22, 177, 27, 6, 131, 126, 187, 108, 190, 218, 231, 66, 189, 13, 124, 223, 96, 167, 159, 191, 203, 227, 123, 9, 0, 71, 166, 2, 17, 0, 0, 0, 5, 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