Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a13a20d3742081b6f916acd19466436424e2dd8e461120c475cdaed151e0aa

Tx prefix hash: f0379d4a8abba724cb1a9a93fc7d0fa7f62226b17f555ef93fbac4d24af81249
Tx public key: 290f11e6abb84b1110d09ad5a6d35149b2ce81e71e50396bb4b56469c58f0bf9
Timestamp: 1764077560 Timestamp [UCT]: 2025-11-25 13:32:40 Age [y:d:h:m:s]: 00:002:03:55:46
Block: 1419855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1556 RingCT/type: yes/0
Extra: 01290f11e6abb84b1110d09ad5a6d35149b2ce81e71e50396bb4b56469c58f0bf902110000000a8ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bae4867bb904c10b589fe88fda89f75ec8d7f0e20d3a5b7c0984620f30a2cff 0.600000000000 1908396 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": 1419865, "vin": [ { "gen": { "height": 1419855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bae4867bb904c10b589fe88fda89f75ec8d7f0e20d3a5b7c0984620f30a2cff" } } ], "extra": [ 1, 41, 15, 17, 230, 171, 184, 75, 17, 16, 208, 154, 213, 166, 211, 81, 73, 178, 206, 129, 231, 30, 80, 57, 107, 180, 181, 100, 105, 197, 143, 11, 249, 2, 17, 0, 0, 0, 10, 140, 235, 127, 9, 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