Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e16ab93dec07b706211cedcfbd2a80f099c768637a57e7996f4804435ddf01c

Tx prefix hash: ef3b268d749d6c9aea29d4b02390ebaaab691eef8a3b81f7a169bdda04e7c733
Tx public key: 35c945de1f6d86e80e771f0376bbc27f4962de0c6edae9b6e298b021575ec156
Timestamp: 1735092231 Timestamp [UCT]: 2024-12-25 02:03:51 Age [y:d:h:m:s]: 00:101:10:14:24
Block: 1182571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72272 RingCT/type: yes/0
Extra: 0135c945de1f6d86e80e771f0376bbc27f4962de0c6edae9b6e298b021575ec1560211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1a39c992e461eec6bd353cd71392a3e3c1a115a8a2bcf1e74045ffdcfb60a04 0.600000000000 1669006 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": 1182581, "vin": [ { "gen": { "height": 1182571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1a39c992e461eec6bd353cd71392a3e3c1a115a8a2bcf1e74045ffdcfb60a04" } } ], "extra": [ 1, 53, 201, 69, 222, 31, 109, 134, 232, 14, 119, 31, 3, 118, 187, 194, 127, 73, 98, 222, 12, 110, 218, 233, 182, 226, 152, 176, 33, 87, 94, 193, 86, 2, 17, 0, 0, 0, 4, 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