Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2665f598528f2a1e322e0c3257ec773af9f096130a9852378916460afc809549

Tx prefix hash: 12f8ae12a566d922ef6447e916cc2f2140bce8d62f7e84806a4b8b94a68acdb1
Tx public key: 644d53deb14c76aaacfc958f3ccf2ff4faca91e71c70668a08c5acd39ec21a58
Timestamp: 1734628623 Timestamp [UCT]: 2024-12-19 17:17:03 Age [y:d:h:m:s]: 00:025:21:07:50
Block: 1178749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18481 RingCT/type: yes/0
Extra: 01644d53deb14c76aaacfc958f3ccf2ff4faca91e71c70668a08c5acd39ec21a5802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1179bb570f8707fe6d2e3a996d97a0c55ad125ca4d60b1ffd8c4c1e0c7cb2a90 0.600000000000 1665138 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": 1178759, "vin": [ { "gen": { "height": 1178749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1179bb570f8707fe6d2e3a996d97a0c55ad125ca4d60b1ffd8c4c1e0c7cb2a90" } } ], "extra": [ 1, 100, 77, 83, 222, 177, 76, 118, 170, 172, 252, 149, 143, 60, 207, 47, 244, 250, 202, 145, 231, 28, 112, 102, 138, 8, 197, 172, 211, 158, 194, 26, 88, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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