Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89307901ec988e28f86df9c581e2510af3c7685435c7746a6848a9e25225d05f

Tx prefix hash: 38abf22170165f27d4f7006682dc6e680f392cbfcb5ba0a3e1d298c7690d5a8a
Tx public key: 31f254eab0f502f75422c1dd3ee8a86ed8257009e37036d6d181ca3e24aecbc7
Timestamp: 1704174322 Timestamp [UCT]: 2024-01-02 05:45:22 Age [y:d:h:m:s]: 01:312:16:19:05
Block: 926344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482313 RingCT/type: yes/0
Extra: 0131f254eab0f502f75422c1dd3ee8a86ed8257009e37036d6d181ca3e24aecbc70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 630beacbe0a915f4aec3b9cb490cd150e29afcfd31209a0fdccc14a0af477cf1 0.600000000000 1384126 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": 926354, "vin": [ { "gen": { "height": 926344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "630beacbe0a915f4aec3b9cb490cd150e29afcfd31209a0fdccc14a0af477cf1" } } ], "extra": [ 1, 49, 242, 84, 234, 176, 245, 2, 247, 84, 34, 193, 221, 62, 232, 168, 110, 216, 37, 112, 9, 227, 112, 54, 214, 209, 129, 202, 62, 36, 174, 203, 199, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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