Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539e46c4c1c84ea4a7d081da26cfe979f23507648027036d240bfbcd16585a55

Tx prefix hash: 862b0cf61765bce2b36975d018b7b432f0e71c61d101be55164bc6b65088892d
Tx public key: 3dc24af0e6bd983e645c6a780aaf40978ab11dde8b5c3dcaf3a97cf9f99a1ba5
Timestamp: 1738827988 Timestamp [UCT]: 2025-02-06 07:46:28 Age [y:d:h:m:s]: 00:287:23:58:56
Block: 1213213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203587 RingCT/type: yes/0
Extra: 013dc24af0e6bd983e645c6a780aaf40978ab11dde8b5c3dcaf3a97cf9f99a1ba50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9913201ed8397ee1f39b6550f3dd471a2d9e1dae3c88ab95bb10aa4eece25182 0.600000000000 1699990 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": 1213223, "vin": [ { "gen": { "height": 1213213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9913201ed8397ee1f39b6550f3dd471a2d9e1dae3c88ab95bb10aa4eece25182" } } ], "extra": [ 1, 61, 194, 74, 240, 230, 189, 152, 62, 100, 92, 106, 120, 10, 175, 64, 151, 138, 177, 29, 222, 139, 92, 61, 202, 243, 169, 124, 249, 249, 154, 27, 165, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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