Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b37a576a20f73e7ba42254578aeb35f75e19ada50fdaf83cbb03c4925e2c093

Tx prefix hash: 774f4a7641c785b0db1a1a813b1df22a9277f7678a991f36e2b59a4a0e6217da
Tx public key: 37473cb5ec3843580fb26c664634ae4685db2b3720ef25e47080406553e42b85
Timestamp: 1695980534 Timestamp [UCT]: 2023-09-29 09:42:14 Age [y:d:h:m:s]: 01:167:07:21:11
Block: 858630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380631 RingCT/type: yes/0
Extra: 0137473cb5ec3843580fb26c664634ae4685db2b3720ef25e47080406553e42b8502110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.877005707000 dcy

stealth address amount amount idx
00: 003e54da31ae99f8f3ce5e0b1bcf68cc8860b72cd96cc58f02231cef8619a102 0.877005707000 1312814 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": 858640, "vin": [ { "gen": { "height": 858630 } } ], "vout": [ { "amount": 877005707, "target": { "key": "003e54da31ae99f8f3ce5e0b1bcf68cc8860b72cd96cc58f02231cef8619a102" } } ], "extra": [ 1, 55, 71, 60, 181, 236, 56, 67, 88, 15, 178, 108, 102, 70, 52, 174, 70, 133, 219, 43, 55, 32, 239, 37, 228, 112, 128, 64, 101, 83, 228, 43, 133, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 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