Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa74fcc5ebb524aad770c1289733300e1fb29720d962ed51bf21f27a3ff17728

Tx prefix hash: 0b81fe1971bcbcea7e3bb8fb404eea40aa10ba50b8f446ae8ce1b5bb6db3f06a
Tx public key: 6c1452d1e5c7e578d3bf67aa5e132fc78e938600247005ef5e41782bbc3927a6
Timestamp: 1733682817 Timestamp [UCT]: 2024-12-08 18:33:37 Age [y:d:h:m:s]: 00:191:16:33:43
Block: 1170907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136707 RingCT/type: yes/0
Extra: 016c1452d1e5c7e578d3bf67aa5e132fc78e938600247005ef5e41782bbc3927a6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974d6427796cdfd0c80c0cfe22e8c07a1b797bca418ec07d16a78ee0e9259625 0.600000000000 1656642 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": 1170917, "vin": [ { "gen": { "height": 1170907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974d6427796cdfd0c80c0cfe22e8c07a1b797bca418ec07d16a78ee0e9259625" } } ], "extra": [ 1, 108, 20, 82, 209, 229, 199, 229, 120, 211, 191, 103, 170, 94, 19, 47, 199, 142, 147, 134, 0, 36, 112, 5, 239, 94, 65, 120, 43, 188, 57, 39, 166, 2, 17, 0, 0, 0, 2, 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