Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9314f825bc4cfe451d3af3405fb2123bde14d2e1e4e3c290851396a84bd84268

Tx prefix hash: cdebff3bacc6d04367000d613ebde77bcb9fef1d44ab4ca31dd0d8a13b38032c
Tx public key: 968cffe0016502c3c1fbbe3b0b3a2b8e1dd285ac0055032c87d0d0f42eda3552
Timestamp: 1725679106 Timestamp [UCT]: 2024-09-07 03:18:26 Age [y:d:h:m:s]: 00:106:15:03:53
Block: 1104632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76291 RingCT/type: yes/0
Extra: 01968cffe0016502c3c1fbbe3b0b3a2b8e1dd285ac0055032c87d0d0f42eda355202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f4422a1094eef22c77409f5207a89d76c56592e7a15e1d8e306a8d12e8ba8f5 0.600000000000 1581849 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": 1104642, "vin": [ { "gen": { "height": 1104632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f4422a1094eef22c77409f5207a89d76c56592e7a15e1d8e306a8d12e8ba8f5" } } ], "extra": [ 1, 150, 140, 255, 224, 1, 101, 2, 195, 193, 251, 190, 59, 11, 58, 43, 142, 29, 210, 133, 172, 0, 85, 3, 44, 135, 208, 208, 244, 46, 218, 53, 82, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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