Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f76438777fd5f00294a9c6718823cff420c11c446528a893c9567e812034375

Tx prefix hash: 0edbc8ee9fa771d74048348864885067cc6fa48ca07aae88b967a0b8bb0460fb
Tx public key: de17eb8670f5d9a0d250fb6b35e0e5b05a8b1d406cd0ae5cf3da4e1adf107450
Timestamp: 1725288171 Timestamp [UCT]: 2024-09-02 14:42:51 Age [y:d:h:m:s]: 00:219:13:03:33
Block: 1101397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156763 RingCT/type: yes/0
Extra: 01de17eb8670f5d9a0d250fb6b35e0e5b05a8b1d406cd0ae5cf3da4e1adf107450021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1167ae324809e03dca56699b2c30c4b155eef9388483cd9b18e8c2ae04a2636 0.600000000000 1577430 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": 1101407, "vin": [ { "gen": { "height": 1101397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1167ae324809e03dca56699b2c30c4b155eef9388483cd9b18e8c2ae04a2636" } } ], "extra": [ 1, 222, 23, 235, 134, 112, 245, 217, 160, 210, 80, 251, 107, 53, 224, 229, 176, 90, 139, 29, 64, 108, 208, 174, 92, 243, 218, 78, 26, 223, 16, 116, 80, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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