Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3afae3afd477ee0929ce264cbbb2791f178c0a9a7b482d513a7b8c8264165e3

Tx prefix hash: d2392c58c357e892cb6b8400271e1cb5b549472fc2a5ce8fd1e27ad60d18aa73
Tx public key: 87b49aaed7c38f58f713ebb6b4fc2c9196d4cdd80eb39f6d874e4662e898a503
Timestamp: 1705666285 Timestamp [UCT]: 2024-01-19 12:11:25 Age [y:d:h:m:s]: 01:292:16:52:33
Block: 938689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468021 RingCT/type: yes/0
Extra: 0187b49aaed7c38f58f713ebb6b4fc2c9196d4cdd80eb39f6d874e4662e898a5030211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f2aa7a37f42ea3dd17121b7bc4aeb36987b5c1fbe5798223861cf29ea6e10e 0.600000000000 1396761 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": 938699, "vin": [ { "gen": { "height": 938689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f2aa7a37f42ea3dd17121b7bc4aeb36987b5c1fbe5798223861cf29ea6e10e" } } ], "extra": [ 1, 135, 180, 154, 174, 215, 195, 143, 88, 247, 19, 235, 182, 180, 252, 44, 145, 150, 212, 205, 216, 14, 179, 159, 109, 135, 78, 70, 98, 232, 152, 165, 3, 2, 17, 0, 0, 0, 4, 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