Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b804113fb06ab2291b95daf3f976f9e9d1d5f70dcb38fb645de3cae7db500889

Tx prefix hash: 61e8e860f63f0f3da865bd11a2960bec8dda3c210f4318f413e773a3f5b0f84a
Tx public key: 833add1470483b17a6e83afc7131b2c471b80744005f929cde19ce1a38757a05
Timestamp: 1705819366 Timestamp [UCT]: 2024-01-21 06:42:46 Age [y:d:h:m:s]: 01:317:12:43:26
Block: 939950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485821 RingCT/type: yes/0
Extra: 01833add1470483b17a6e83afc7131b2c471b80744005f929cde19ce1a38757a050211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b446f10d4a995ba84f0ea9a344dc097db5a52c4b24702b974ad587713a983882 0.600000000000 1398084 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": 939960, "vin": [ { "gen": { "height": 939950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b446f10d4a995ba84f0ea9a344dc097db5a52c4b24702b974ad587713a983882" } } ], "extra": [ 1, 131, 58, 221, 20, 112, 72, 59, 23, 166, 232, 58, 252, 113, 49, 178, 196, 113, 184, 7, 68, 0, 95, 146, 156, 222, 25, 206, 26, 56, 117, 122, 5, 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