Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234499b909beb723c6772143789e19d69088a8d5a1d30c883d7d37e066b948d5

Tx prefix hash: 188a51fab4a3772e8bc2de7241a74082c2d4364e24caae6a71250bfcd05d88e1
Tx public key: 9f1f0668748506d9c8a68a204b4e9489dd7eb7684bc6a2bcdbde41bf7110ee16
Timestamp: 1699557591 Timestamp [UCT]: 2023-11-09 19:19:51 Age [y:d:h:m:s]: 01:356:16:32:50
Block: 888080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513830 RingCT/type: yes/0
Extra: 019f1f0668748506d9c8a68a204b4e9489dd7eb7684bc6a2bcdbde41bf7110ee160211000000064b8f5122000000000000000000

1 output(s) for total of 0.700522843000 dcy

stealth address amount amount idx
00: 01924f710c7eed4aa51091b0e2b4082fa204ca878fc2aecedb81a31500f296a4 0.700522843000 1343999 of 0

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": 888090, "vin": [ { "gen": { "height": 888080 } } ], "vout": [ { "amount": 700522843, "target": { "key": "01924f710c7eed4aa51091b0e2b4082fa204ca878fc2aecedb81a31500f296a4" } } ], "extra": [ 1, 159, 31, 6, 104, 116, 133, 6, 217, 200, 166, 138, 32, 75, 78, 148, 137, 221, 126, 183, 104, 75, 198, 162, 188, 219, 222, 65, 191, 113, 16, 238, 22, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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