Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b857b1436918359d917b5c5b8eb11ec6914155aecace7f010717d137b7fc8d20

Tx prefix hash: c6f0f7dd7c216f4c47d72d247c96fbf618e41747d1bbbaf4b9d0584def9817b6
Tx public key: 35c1fea3988079878b65e7348e410639b30b570374f8a9b572daac46ade91e84
Timestamp: 1715921659 Timestamp [UCT]: 2024-05-17 04:54:19 Age [y:d:h:m:s]: 00:327:16:47:21
Block: 1023748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234226 RingCT/type: yes/0
Extra: 0135c1fea3988079878b65e7348e410639b30b570374f8a9b572daac46ade91e840211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eea30b4d4dc50ae65c9035f67e3505fefaadb0280d1c67d59b2fc976ae4e39db 0.600000000000 1488951 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": 1023758, "vin": [ { "gen": { "height": 1023748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eea30b4d4dc50ae65c9035f67e3505fefaadb0280d1c67d59b2fc976ae4e39db" } } ], "extra": [ 1, 53, 193, 254, 163, 152, 128, 121, 135, 139, 101, 231, 52, 142, 65, 6, 57, 179, 11, 87, 3, 116, 248, 169, 181, 114, 218, 172, 70, 173, 233, 30, 132, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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