Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69fee48ac007625edd0fd7e99f0cc862e3e8f1b44e8cb46be96f1c1cc340caa1

Tx prefix hash: 5d99d091050b70902b60d7ccb1a973301e6b7086d86632b008bace515f06e46e
Tx public key: c98d721fb28b7272c89baabf9e9fa39a597fb9af446497637887585ecc19ca00
Timestamp: 1683371230 Timestamp [UCT]: 2023-05-06 11:07:10 Age [y:d:h:m:s]: 02:185:11:09:29
Block: 754136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652369 RingCT/type: yes/0
Extra: 01c98d721fb28b7272c89baabf9e9fa39a597fb9af446497637887585ecc19ca00021100000005faf35c9c000000000000000000

1 output(s) for total of 1.946411099000 dcy

stealth address amount amount idx
00: f73421edbe20a8dfb0def182c719c87da03c82ec74fa7c2a3e65d7171506dc09 1.946411099000 1202389 of 0

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": 754146, "vin": [ { "gen": { "height": 754136 } } ], "vout": [ { "amount": 1946411099, "target": { "key": "f73421edbe20a8dfb0def182c719c87da03c82ec74fa7c2a3e65d7171506dc09" } } ], "extra": [ 1, 201, 141, 114, 31, 178, 139, 114, 114, 200, 155, 170, 191, 158, 159, 163, 154, 89, 127, 185, 175, 68, 100, 151, 99, 120, 135, 88, 94, 204, 25, 202, 0, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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