Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6dfa37182e13335ec3203d6cddbd35ead3e69317541ad50e70bf99f885e0ff

Tx prefix hash: 2e9711fd3cb024de2eb1794e46e7c6dfcd565395719270bd98bcffd3e5813dfd
Tx public key: ea2129c1e9bdf73f1f1cedad077e88cf6ee7fe16e852f4e788b76e623f326c1f
Timestamp: 1734367970 Timestamp [UCT]: 2024-12-16 16:52:50 Age [y:d:h:m:s]: 00:173:06:57:01
Block: 1176582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123667 RingCT/type: yes/0
Extra: 01ea2129c1e9bdf73f1f1cedad077e88cf6ee7fe16e852f4e788b76e623f326c1f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ea0a875b904e9e408aa5ee1b974e7e0def45e7187d969b719a26fa6c8798a3e 0.600000000000 1662935 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": 1176592, "vin": [ { "gen": { "height": 1176582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ea0a875b904e9e408aa5ee1b974e7e0def45e7187d969b719a26fa6c8798a3e" } } ], "extra": [ 1, 234, 33, 41, 193, 233, 189, 247, 63, 31, 28, 237, 173, 7, 126, 136, 207, 110, 231, 254, 22, 232, 82, 244, 231, 136, 183, 110, 98, 63, 50, 108, 31, 2, 17, 0, 0, 0, 3, 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