Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1135b92894eaa6213868cac080651cc9eb44ea113d52d57c966e63992610d4d8

Tx prefix hash: 2da4c18b627b1cffecf4639d2aaea4cd251d1c08a61bbd5caa94cf2f1232cec6
Tx public key: 8513b5181cf89f09c0472ea2df2c058b81173c9b98c8a6faffc55020bf746362
Timestamp: 1761675518 Timestamp [UCT]: 2025-10-28 18:18:38 Age [y:d:h:m:s]: 00:023:03:41:39
Block: 1399954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16564 RingCT/type: yes/0
Extra: 018513b5181cf89f09c0472ea2df2c058b81173c9b98c8a6faffc55020bf74636202110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed92653274239e1ba63ed2b7e515319d68360aff06fd540c2c7a78e9fa1f4405 0.600000000000 1888261 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": 1399964, "vin": [ { "gen": { "height": 1399954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed92653274239e1ba63ed2b7e515319d68360aff06fd540c2c7a78e9fa1f4405" } } ], "extra": [ 1, 133, 19, 181, 24, 28, 248, 159, 9, 192, 71, 46, 162, 223, 44, 5, 139, 129, 23, 60, 155, 152, 200, 166, 250, 255, 197, 80, 32, 191, 116, 99, 98, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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