Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d25cef04705b9a97b825b881531c94354e1a0e9e70405a512ea9068b417681fc

Tx prefix hash: 33419eab4432fead9f426012fc3b07fbecd6da2f20535c55b446bf359aaac240
Tx public key: 234fa5e6e0ec8b68189e74e9c198b6479369f8a33a656a54843ea78cb08ae17c
Timestamp: 1695035966 Timestamp [UCT]: 2023-09-18 11:19:26 Age [y:d:h:m:s]: 01:004:01:02:47
Block: 850790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264155 RingCT/type: yes/0
Extra: 01234fa5e6e0ec8b68189e74e9c198b6479369f8a33a656a54843ea78cb08ae17c02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.931064152000 dcy

stealth address amount amount idx
00: 28ee6bf150bfb7467260bed8610f6276ce8298cf72e419f99105c9ddf25d7e4e 0.931064152000 1304526 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": 850800, "vin": [ { "gen": { "height": 850790 } } ], "vout": [ { "amount": 931064152, "target": { "key": "28ee6bf150bfb7467260bed8610f6276ce8298cf72e419f99105c9ddf25d7e4e" } } ], "extra": [ 1, 35, 79, 165, 230, 224, 236, 139, 104, 24, 158, 116, 233, 193, 152, 182, 71, 147, 105, 248, 163, 58, 101, 106, 84, 132, 62, 167, 140, 176, 138, 225, 124, 2, 17, 0, 0, 0, 13, 230, 210, 127, 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