Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f4403993799cb4c4c93c63521a91856e9d6be2ab80c33d1fb0a0e6398d7b665

Tx prefix hash: f02601347b3c6615799169aa6fe921c1bbed776d841387e5ddc0fa31e49d4d0e
Tx public key: 330d51d3d769b9ba5dd6eff639a31f1e64a94044f4f4bad6a72251d36c55a700
Timestamp: 1711745544 Timestamp [UCT]: 2024-03-29 20:52:24 Age [y:d:h:m:s]: 01:064:11:46:27
Block: 989140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307090 RingCT/type: yes/0
Extra: 01330d51d3d769b9ba5dd6eff639a31f1e64a94044f4f4bad6a72251d36c55a7000211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0933442a58a7177ad8c5bc6ecaef31b76568953cb958b468c1f143ecf63cffc6 0.600000000000 1449435 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": 989150, "vin": [ { "gen": { "height": 989140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0933442a58a7177ad8c5bc6ecaef31b76568953cb958b468c1f143ecf63cffc6" } } ], "extra": [ 1, 51, 13, 81, 211, 215, 105, 185, 186, 93, 214, 239, 246, 57, 163, 31, 30, 100, 169, 64, 68, 244, 244, 186, 214, 167, 34, 81, 211, 108, 85, 167, 0, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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