Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c835cd8b63b462d787ef7d630fea7410b99f02d96878081a9bc7b76fc876c0f

Tx prefix hash: 18b3ee7bc5122b54587baa25ea2bb482394c73b43fd1797156f2e66048381302
Tx public key: 9de05a9f903008992404c3432a2fb4a5dc4d63a927255837e9b36e098c2111af
Timestamp: 1735901193 Timestamp [UCT]: 2025-01-03 10:46:33 Age [y:d:h:m:s]: 00:092:16:40:52
Block: 1189276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66003 RingCT/type: yes/0
Extra: 019de05a9f903008992404c3432a2fb4a5dc4d63a927255837e9b36e098c2111af021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eb8db53ca39c05de9469c511a9c4a6fc710d6677df7fa5e4c316b959029859d 0.600000000000 1675783 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": 1189286, "vin": [ { "gen": { "height": 1189276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eb8db53ca39c05de9469c511a9c4a6fc710d6677df7fa5e4c316b959029859d" } } ], "extra": [ 1, 157, 224, 90, 159, 144, 48, 8, 153, 36, 4, 195, 67, 42, 47, 180, 165, 220, 77, 99, 169, 39, 37, 88, 55, 233, 179, 110, 9, 140, 33, 17, 175, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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