Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25685f4bb7bcaac872196835feca7deaf6f29e439c34e073fe2e36cf5b888aad

Tx prefix hash: e2edc79cc9adfc389cd8eef3ac07cea0ef2c4b64881b86d1620ffd96981d5620
Tx public key: 475ac8dd81a2e038f2e0c1a36c70c0f9053dcbf330eb6ada4b9edcc044da61fb
Timestamp: 1724318619 Timestamp [UCT]: 2024-08-22 09:23:39 Age [y:d:h:m:s]: 00:233:11:45:31
Block: 1093373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166724 RingCT/type: yes/0
Extra: 01475ac8dd81a2e038f2e0c1a36c70c0f9053dcbf330eb6ada4b9edcc044da61fb02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db1d5c163ccf3c6ce4888de62a5bb8f63b862e9ce8010ca5f2539af33251d0a1 0.600000000000 1568304 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": 1093383, "vin": [ { "gen": { "height": 1093373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db1d5c163ccf3c6ce4888de62a5bb8f63b862e9ce8010ca5f2539af33251d0a1" } } ], "extra": [ 1, 71, 90, 200, 221, 129, 162, 224, 56, 242, 224, 193, 163, 108, 112, 192, 249, 5, 61, 203, 243, 48, 235, 106, 218, 75, 158, 220, 192, 68, 218, 97, 251, 2, 17, 0, 0, 0, 10, 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