Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b5b1c42dd8f4050369c870f511c6b05d326b65e65d85ec9a791ba740f325db

Tx prefix hash: 9d4085530221ea2551021533a45712ba1a9740f80c4222a7eb7647aee89e3419
Tx public key: 38c172ededa834cae7f783e8a65983a9bb8a6c972d5d6e5428e95a7cd9a5a17b
Timestamp: 1729609639 Timestamp [UCT]: 2024-10-22 15:07:19 Age [y:d:h:m:s]: 00:198:01:20:05
Block: 1137186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141367 RingCT/type: yes/0
Extra: 0138c172ededa834cae7f783e8a65983a9bb8a6c972d5d6e5428e95a7cd9a5a17b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e33393ea1d9accf2886e31efd7ffbb337b74429251fec77089947e7680e326e 0.600000000000 1620631 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": 1137196, "vin": [ { "gen": { "height": 1137186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e33393ea1d9accf2886e31efd7ffbb337b74429251fec77089947e7680e326e" } } ], "extra": [ 1, 56, 193, 114, 237, 237, 168, 52, 202, 231, 247, 131, 232, 166, 89, 131, 169, 187, 138, 108, 151, 45, 93, 110, 84, 40, 233, 90, 124, 217, 165, 161, 123, 2, 17, 0, 0, 0, 5, 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