Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01d68b7d7cf4ef2064b449b53c86e8b5537a1e93741650f35f605113f9aa95f

Tx prefix hash: ef37e02a0b05509b9c1d2336c73be0dddf54dd0200402515a451d4705411d09f
Tx public key: cc14fa510765532e4479239e9e521c3c7ed86e9d407d966e0aa9c3c6791bdfc2
Timestamp: 1732090638 Timestamp [UCT]: 2024-11-20 08:17:18 Age [y:d:h:m:s]: 00:154:03:38:51
Block: 1157687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110012 RingCT/type: yes/0
Extra: 01cc14fa510765532e4479239e9e521c3c7ed86e9d407d966e0aa9c3c6791bdfc20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be0e54e759ebae83aac708f5adfc1fa686b7ab65b444cdf0344b08d62183178 0.600000000000 1643310 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": 1157697, "vin": [ { "gen": { "height": 1157687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be0e54e759ebae83aac708f5adfc1fa686b7ab65b444cdf0344b08d62183178" } } ], "extra": [ 1, 204, 20, 250, 81, 7, 101, 83, 46, 68, 121, 35, 158, 158, 82, 28, 60, 126, 216, 110, 157, 64, 125, 150, 110, 10, 169, 195, 198, 121, 27, 223, 194, 2, 17, 0, 0, 0, 3, 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