Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 332c36e757802acc35a71252a23b893c2c584edbe082fa43d06c51ba0d27a54c

Tx prefix hash: cc71a4df2b5abd0d2f47c8b1e58a03db68874ecc057bc590e36b0697908ecaa4
Tx public key: ae793b949ae9eb9862438e9c4bf04f2a3ae614448cb6cfa777fd95eb55fb8905
Timestamp: 1735216612 Timestamp [UCT]: 2024-12-26 12:36:52 Age [y:d:h:m:s]: 00:086:17:12:26
Block: 1183605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61742 RingCT/type: yes/0
Extra: 01ae793b949ae9eb9862438e9c4bf04f2a3ae614448cb6cfa777fd95eb55fb89050211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83fbcdd6cd641f2eae0edaaaac3f613a2f8602a314d7b14c29f4cedd4217aa9f 0.600000000000 1670050 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": 1183615, "vin": [ { "gen": { "height": 1183605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83fbcdd6cd641f2eae0edaaaac3f613a2f8602a314d7b14c29f4cedd4217aa9f" } } ], "extra": [ 1, 174, 121, 59, 148, 154, 233, 235, 152, 98, 67, 142, 156, 75, 240, 79, 42, 58, 230, 20, 68, 140, 182, 207, 167, 119, 253, 149, 235, 85, 251, 137, 5, 2, 17, 0, 0, 0, 9, 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