Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a2dbe8772a976ac0c43f606055b1ff79993737632ce6e5dd723e4ff119c219

Tx prefix hash: 93496f685b55d0b85ad48ddb049084ca5b09bd4f5b5dbbfa30e56e48ab8617f4
Tx public key: 0bdf32c88bd1b27eb8b92cc5d68851417d7a5da671a72cc0c0fbf354beca110d
Timestamp: 1700328662 Timestamp [UCT]: 2023-11-18 17:31:02 Age [y:d:h:m:s]: 01:165:08:28:36
Block: 894468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379373 RingCT/type: yes/0
Extra: 010bdf32c88bd1b27eb8b92cc5d68851417d7a5da671a72cc0c0fbf354beca110d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.667200244000 dcy

stealth address amount amount idx
00: 27c5d26d49b2fda16670c1117583f3ed43970a16e265e74a6f594e2493205edd 0.667200244000 1350669 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": 894478, "vin": [ { "gen": { "height": 894468 } } ], "vout": [ { "amount": 667200244, "target": { "key": "27c5d26d49b2fda16670c1117583f3ed43970a16e265e74a6f594e2493205edd" } } ], "extra": [ 1, 11, 223, 50, 200, 139, 209, 178, 126, 184, 185, 44, 197, 214, 136, 81, 65, 125, 122, 93, 166, 113, 167, 44, 192, 192, 251, 243, 84, 190, 202, 17, 13, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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