Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9dbdf1e6fd4ab4c5ceef0c61224cf465ae1de420967c876b3362b1848fa2a96

Tx prefix hash: da2d9030e6f8bfa38c6c0eb157d3e3e7a576c61861ee342ccf619cac3ab3b119
Tx public key: 9c955e78e496edef4815f2a2949b08481c50f9fb0dcc4ded21a1d01e158ee9ab
Timestamp: 1705648921 Timestamp [UCT]: 2024-01-19 07:22:01 Age [y:d:h:m:s]: 01:296:17:52:52
Block: 938551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470902 RingCT/type: yes/0
Extra: 019c955e78e496edef4815f2a2949b08481c50f9fb0dcc4ded21a1d01e158ee9ab0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbb25f6f72d9d2dbf0d7e3cf5a7be2f7f7af4519640ee0de3d0aaf4203a9ae09 0.600000000000 1396621 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": 938561, "vin": [ { "gen": { "height": 938551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbb25f6f72d9d2dbf0d7e3cf5a7be2f7f7af4519640ee0de3d0aaf4203a9ae09" } } ], "extra": [ 1, 156, 149, 94, 120, 228, 150, 237, 239, 72, 21, 242, 162, 148, 155, 8, 72, 28, 80, 249, 251, 13, 204, 77, 237, 33, 161, 208, 30, 21, 142, 233, 171, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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