Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd798e38048fe1703c24b14e931c2bce9e0e61d5aaff9bc98dad9dddb54e40b9

Tx prefix hash: 5e94c11af73e9a96989a5fc255580607178c2f3c237410174473ccfabb7d0e8c
Tx public key: 362d8045288d513b0c86c11b649a5ed7b25a1d0b8719b02eaeb0468bc21b20ca
Timestamp: 1702503246 Timestamp [UCT]: 2023-12-13 21:34:06 Age [y:d:h:m:s]: 01:125:19:26:05
Block: 912498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351053 RingCT/type: yes/0
Extra: 01362d8045288d513b0c86c11b649a5ed7b25a1d0b8719b02eaeb0468bc21b20ca021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c285f1d601c9fb944fdde11dfbf44c48295901e96b4ba68fac69c42b63d43c0f 0.600000000000 1369726 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": 912508, "vin": [ { "gen": { "height": 912498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c285f1d601c9fb944fdde11dfbf44c48295901e96b4ba68fac69c42b63d43c0f" } } ], "extra": [ 1, 54, 45, 128, 69, 40, 141, 81, 59, 12, 134, 193, 27, 100, 154, 94, 215, 178, 90, 29, 11, 135, 25, 176, 46, 174, 176, 70, 139, 194, 27, 32, 202, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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