Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ae91e3752fa2ee0b3053d0c5340bed61b69329cc813bc45d2b3f43e38e6ea7

Tx prefix hash: ff3b55accaff9ac487c83e3af4c14b2fd0bc352ae5864a702faf8d5c89acd3ab
Tx public key: 430cd8050197c5a29721f5d6819260f80b701456803dbbf3b56a66fff349b5b5
Timestamp: 1707638719 Timestamp [UCT]: 2024-02-11 08:05:19 Age [y:d:h:m:s]: 01:281:23:57:07
Block: 955066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460322 RingCT/type: yes/0
Extra: 01430cd8050197c5a29721f5d6819260f80b701456803dbbf3b56a66fff349b5b5021100000008b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d2087c1eef8780e51bd430310c212c4da35eb1ab7416286f047ad9ebc2afa1 0.600000000000 1414348 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": 955076, "vin": [ { "gen": { "height": 955066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d2087c1eef8780e51bd430310c212c4da35eb1ab7416286f047ad9ebc2afa1" } } ], "extra": [ 1, 67, 12, 216, 5, 1, 151, 197, 162, 151, 33, 245, 214, 129, 146, 96, 248, 11, 112, 20, 86, 128, 61, 187, 243, 181, 106, 102, 255, 243, 73, 181, 181, 2, 17, 0, 0, 0, 8, 182, 226, 220, 51, 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