Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ad29d8549c210e912916702effbf6a554c3f9e9969a12d9aed865f4209a80a

Tx prefix hash: 3ad31fae1fc167f1ed6d7bbbce4c21c6f1e8ba922059fd6d9b6acd3bbfd6e639
Tx public key: 6bc1d64fd8de1633b4d29ee88d035c76824defb693a08f21449f082b46696344
Timestamp: 1739017190 Timestamp [UCT]: 2025-02-08 12:19:50 Age [y:d:h:m:s]: 00:285:13:12:32
Block: 1214788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201828 RingCT/type: yes/0
Extra: 016bc1d64fd8de1633b4d29ee88d035c76824defb693a08f21449f082b46696344021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a3359e912b04de94606028d8df44b9627e0fe275cfbb5464209bbd988ea53e4 0.600000000000 1701583 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": 1214798, "vin": [ { "gen": { "height": 1214788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a3359e912b04de94606028d8df44b9627e0fe275cfbb5464209bbd988ea53e4" } } ], "extra": [ 1, 107, 193, 214, 79, 216, 222, 22, 51, 180, 210, 158, 232, 141, 3, 92, 118, 130, 77, 239, 182, 147, 160, 143, 33, 68, 159, 8, 43, 70, 105, 99, 68, 2, 17, 0, 0, 0, 3, 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