Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd6c017511c8bb68dcb1171a0368d919d3a81dd8e96dc898f463c5afa83cbe19

Tx prefix hash: ae7f43d5b1a526391237ac65b98691fe89c3cfa1a442ac049756eb3850efeae1
Tx public key: 0fa68e8fb948116e4ae31cc8a2488fca812f47a769d1282ada606eeea51a5f77
Timestamp: 1680989217 Timestamp [UCT]: 2023-04-08 21:26:57 Age [y:d:h:m:s]: 02:006:00:59:16
Block: 734433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526439 RingCT/type: yes/0
Extra: 010fa68e8fb948116e4ae31cc8a2488fca812f47a769d1282ada606eeea51a5f770211000000075029cbac000000000000000000

1 output(s) for total of 2.262136563000 dcy

stealth address amount amount idx
00: 26dcb42dcc34319c0396ead98072332b8b2cbbc866e1f0177e27ac8cea16cc42 2.262136563000 1180636 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": 734443, "vin": [ { "gen": { "height": 734433 } } ], "vout": [ { "amount": 2262136563, "target": { "key": "26dcb42dcc34319c0396ead98072332b8b2cbbc866e1f0177e27ac8cea16cc42" } } ], "extra": [ 1, 15, 166, 142, 143, 185, 72, 17, 110, 74, 227, 28, 200, 162, 72, 143, 202, 129, 47, 71, 167, 105, 209, 40, 42, 218, 96, 110, 238, 165, 26, 95, 119, 2, 17, 0, 0, 0, 7, 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