Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5668da8e37e07aa79b2b98ebff01c1136dacf26b3d07c606d814ad0a45ed02d2

Tx prefix hash: 3b26d8725e0d1a3e6ba4486924454bcf441e0874e580cdd3dd8813b6a62e8fa5
Tx public key: 740cd89e09e53bc38f4d249679bed2fcdfcd615ae53d9086fda781547fe419c0
Timestamp: 1738122663 Timestamp [UCT]: 2025-01-29 03:51:03 Age [y:d:h:m:s]: 00:341:17:38:08
Block: 1207386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242077 RingCT/type: yes/0
Extra: 01740cd89e09e53bc38f4d249679bed2fcdfcd615ae53d9086fda781547fe419c0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 602b7a280b6fe782fe99b896b9e504f857fb55b2a872280b22a34dc84bcff730 0.600000000000 1694109 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": 1207396, "vin": [ { "gen": { "height": 1207386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "602b7a280b6fe782fe99b896b9e504f857fb55b2a872280b22a34dc84bcff730" } } ], "extra": [ 1, 116, 12, 216, 158, 9, 229, 59, 195, 143, 77, 36, 150, 121, 190, 210, 252, 223, 205, 97, 90, 229, 61, 144, 134, 253, 167, 129, 84, 127, 228, 25, 192, 2, 17, 0, 0, 0, 2, 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