Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c24b7699a23f2e84e686192fdce056ee8075b0163cadcace7591cb777601ee

Tx prefix hash: 9ca9fb591f2d2082dca303fc4dec73708ae9d0dc509caaffc7c96dd2e5a13372
Tx public key: 55b336de3c745e3f1f73cb3c76afd36c58a14d9717e25d083beac588fb3be58e
Timestamp: 1676365191 Timestamp [UCT]: 2023-02-14 08:59:51 Age [y:d:h:m:s]: 02:048:08:10:04
Block: 696688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556143 RingCT/type: yes/0
Extra: 0155b336de3c745e3f1f73cb3c76afd36c58a14d9717e25d083beac588fb3be58e0211000000025029cbac000000000000000000

1 output(s) for total of 3.017055958000 dcy

stealth address amount amount idx
00: 5f943e11d97d00fed17ae4cadea559092e144215f6672951b2ad6f66bd583fe5 3.017055958000 1139729 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": 696698, "vin": [ { "gen": { "height": 696688 } } ], "vout": [ { "amount": 3017055958, "target": { "key": "5f943e11d97d00fed17ae4cadea559092e144215f6672951b2ad6f66bd583fe5" } } ], "extra": [ 1, 85, 179, 54, 222, 60, 116, 94, 63, 31, 115, 203, 60, 118, 175, 211, 108, 88, 161, 77, 151, 23, 226, 93, 8, 59, 234, 197, 136, 251, 59, 229, 142, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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