Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e96d5131801b628ad7ecb5ce85c7f6aef18ae2dc92aad65dac8d799e909ab7b

Tx prefix hash: 07ee74c30ce47d40a2d503b08cbd0d46731bab0c53e7da4c45054385a03a96e1
Tx public key: 272b7fa718d6439f4489124d9367d16eb6f9818bcf5353e8018bbbf5a2efc652
Timestamp: 1766012784 Timestamp [UCT]: 2025-12-17 23:06:24 Age [y:d:h:m:s]: 00:003:21:44:23
Block: 1435884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2792 RingCT/type: yes/0
Extra: 01272b7fa718d6439f4489124d9367d16eb6f9818bcf5353e8018bbbf5a2efc6520211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa80f9405369f38c7df3e146c9a216c48a94a43d7f7dc8ac2553b98a0e7f6f06 0.600000000000 1924689 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": 1435894, "vin": [ { "gen": { "height": 1435884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa80f9405369f38c7df3e146c9a216c48a94a43d7f7dc8ac2553b98a0e7f6f06" } } ], "extra": [ 1, 39, 43, 127, 167, 24, 214, 67, 159, 68, 137, 18, 77, 147, 103, 209, 110, 182, 249, 129, 139, 207, 83, 83, 232, 1, 139, 187, 245, 162, 239, 198, 82, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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