Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03015799bb9277bece693b4c00c5c4047c4beb766dc419338a85d5945f7259f1

Tx prefix hash: 0450bdd6db41d53382038369afe25cd71998ff097098b81315b7ac4bb65f5c46
Tx public key: 3eccb752f540e3f99b9bd41ad0aa3358c9a7bd90bdfefa471fc6b2dd533638f0
Timestamp: 1725187970 Timestamp [UCT]: 2024-09-01 10:52:50 Age [y:d:h:m:s]: 00:051:23:41:29
Block: 1100573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37201 RingCT/type: yes/0
Extra: 013eccb752f540e3f99b9bd41ad0aa3358c9a7bd90bdfefa471fc6b2dd533638f002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc98f0e845ad43d73c0b859bc12e4e94bd52a1815bba307f6d82b91fda5aa9f4 0.600000000000 1576552 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": 1100583, "vin": [ { "gen": { "height": 1100573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc98f0e845ad43d73c0b859bc12e4e94bd52a1815bba307f6d82b91fda5aa9f4" } } ], "extra": [ 1, 62, 204, 183, 82, 245, 64, 227, 249, 155, 155, 212, 26, 208, 170, 51, 88, 201, 167, 189, 144, 189, 254, 250, 71, 31, 198, 178, 221, 83, 54, 56, 240, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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