Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f8df1728b095a95794d8781a51befe114726ed9807c0dc4c1fbf8726cac72c5

Tx prefix hash: 3c66439a58e013b900aabcabc6bec3f14193e6c3640d2feb907e480b5b973e52
Tx public key: 000ba8e8a637c39e37ad8b2fbafdd28a595caa16bd0e6ae1464aafa013871a6d
Timestamp: 1733283048 Timestamp [UCT]: 2024-12-04 03:30:48 Age [y:d:h:m:s]: 00:110:10:54:31
Block: 1167579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78737 RingCT/type: yes/0
Extra: 01000ba8e8a637c39e37ad8b2fbafdd28a595caa16bd0e6ae1464aafa013871a6d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9950662f69ccfbaccf2605c2ee3f2a3284d44542526ab213a7911eed09451213 0.600000000000 1653276 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": 1167589, "vin": [ { "gen": { "height": 1167579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9950662f69ccfbaccf2605c2ee3f2a3284d44542526ab213a7911eed09451213" } } ], "extra": [ 1, 0, 11, 168, 232, 166, 55, 195, 158, 55, 173, 139, 47, 186, 253, 210, 138, 89, 92, 170, 22, 189, 14, 106, 225, 70, 74, 175, 160, 19, 135, 26, 109, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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