Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37df374cc31bb8a7c65b7a0512ae3faeaea5c71605a6e11f63fe121e828e90bf

Tx prefix hash: 4f34c21d16a385cbc5e31f55e519b7fe9b756b135b10aee67eba589f3c9bbfc3
Tx public key: f39343d37df0024e15dd4e1d5634358a46ac3b332c77a4ff97d2f52abedffbcd
Timestamp: 1736738566 Timestamp [UCT]: 2025-01-13 03:22:46 Age [y:d:h:m:s]: 00:342:03:27:44
Block: 1196182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242091 RingCT/type: yes/0
Extra: 01f39343d37df0024e15dd4e1d5634358a46ac3b332c77a4ff97d2f52abedffbcd021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd51e08204d189912c46bbc8fc775b3d3cec45d12ac0d3636ca5f8a0b989669 0.600000000000 1682779 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": 1196192, "vin": [ { "gen": { "height": 1196182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd51e08204d189912c46bbc8fc775b3d3cec45d12ac0d3636ca5f8a0b989669" } } ], "extra": [ 1, 243, 147, 67, 211, 125, 240, 2, 78, 21, 221, 78, 29, 86, 52, 53, 138, 70, 172, 59, 51, 44, 119, 164, 255, 151, 210, 245, 42, 190, 223, 251, 205, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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