Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba88ee68de8a8067b1f86cc60a271d627e01f2782ce310aa0c1413ffb0912c1b

Tx prefix hash: 65dcd3c01407811553d8f5ec0ef5e0188d9da004882ebf243f4910d8922ac779
Tx public key: f78b9635e2a0719ad699fa31cc5c0bd04627817eca3cf102c38234a0a35a08c7
Timestamp: 1709044975 Timestamp [UCT]: 2024-02-27 14:42:55 Age [y:d:h:m:s]: 01:297:19:14:17
Block: 966743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471614 RingCT/type: yes/0
Extra: 01f78b9635e2a0719ad699fa31cc5c0bd04627817eca3cf102c38234a0a35a08c702110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7473c49358d8f8c67a734d632a912a020416a4cd2cca4f7e18a46e3b7dbe3f8 0.600000000000 1426514 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": 966753, "vin": [ { "gen": { "height": 966743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7473c49358d8f8c67a734d632a912a020416a4cd2cca4f7e18a46e3b7dbe3f8" } } ], "extra": [ 1, 247, 139, 150, 53, 226, 160, 113, 154, 214, 153, 250, 49, 204, 92, 11, 208, 70, 39, 129, 126, 202, 60, 241, 2, 195, 130, 52, 160, 163, 90, 8, 199, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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