Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f3b8cc64d9540c7b4342d2033391972a3c908410c81a4691399f436341fc0e

Tx prefix hash: dac09d081a9957dfbb2b8e0eb2aa7bcc6fc44abb746e61dbd2e29b7a86a8637f
Tx public key: 4dd7e5ec8c305f4a7fd7f525b9170bee2fc167510d4dc5db533a912e3d622e6f
Timestamp: 1582217551 Timestamp [UCT]: 2020-02-20 16:52:31 Age [y:d:h:m:s]: 04:319:18:20:57
Block: 68924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121063 RingCT/type: yes/0
Extra: 014dd7e5ec8c305f4a7fd7f525b9170bee2fc167510d4dc5db533a912e3d622e6f0211000000094ac5aa02000000000000000000

1 output(s) for total of 362.766338469000 dcy

stealth address amount amount idx
00: 5bb87c4b021277e2af7905006010be47aca3b661b95125ffe5dfefabf624bfb3 362.766338469000 127111 of 0

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": 68934, "vin": [ { "gen": { "height": 68924 } } ], "vout": [ { "amount": 362766338469, "target": { "key": "5bb87c4b021277e2af7905006010be47aca3b661b95125ffe5dfefabf624bfb3" } } ], "extra": [ 1, 77, 215, 229, 236, 140, 48, 95, 74, 127, 215, 245, 37, 185, 23, 11, 238, 47, 193, 103, 81, 13, 77, 197, 219, 83, 58, 145, 46, 61, 98, 46, 111, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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