Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5afd4740853e2131602ae0e2dbbea6c631e12ec1709d0477501d9c16f98184e8

Tx prefix hash: dccd1af0d6323cb880f90c4b4620e69346b7c0a264bdac5335e998cd1070086c
Tx public key: 98f3a958be0cddcc5f645072e69ca93f4bc99deb79e7de8d54b07c6beb8946cf
Timestamp: 1693322879 Timestamp [UCT]: 2023-08-29 15:27:59 Age [y:d:h:m:s]: 01:180:20:40:58
Block: 836567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390355 RingCT/type: yes/0
Extra: 0198f3a958be0cddcc5f645072e69ca93f4bc99deb79e7de8d54b07c6beb8946cf02110000000475e3f0e9000000000000000000

1 output(s) for total of 1.037782469000 dcy

stealth address amount amount idx
00: 21b31088b80f2e4792016f69d839cf2daf10ee13fa99e7a63d6e94bde5417787 1.037782469000 1289155 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": 836577, "vin": [ { "gen": { "height": 836567 } } ], "vout": [ { "amount": 1037782469, "target": { "key": "21b31088b80f2e4792016f69d839cf2daf10ee13fa99e7a63d6e94bde5417787" } } ], "extra": [ 1, 152, 243, 169, 88, 190, 12, 221, 204, 95, 100, 80, 114, 230, 156, 169, 63, 75, 201, 157, 235, 121, 231, 222, 141, 84, 176, 124, 107, 235, 137, 70, 207, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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