Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a0e2ef98cce71e2979c830cab9af68f85a28229ffaa31b7e7d170741668cff7

Tx prefix hash: 1e35d13f445f9679c5b12864d4e44f537f70bab0a0992d4de7b5744b5deb30ae
Tx public key: f215e4400005df9af1906cf7f8767a83cd5874c8d6c7f8a4f76303c579c45073
Timestamp: 1761903708 Timestamp [UCT]: 2025-10-31 09:41:48 Age [y:d:h:m:s]: 00:015:06:58:58
Block: 1401851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10931 RingCT/type: yes/0
Extra: 01f215e4400005df9af1906cf7f8767a83cd5874c8d6c7f8a4f76303c579c4507302110000000c8368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adfb6ae5cffd42002d1b12f216379780419e4b0d54575ca325e7981795beee9d 0.600000000000 1890170 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": 1401861, "vin": [ { "gen": { "height": 1401851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adfb6ae5cffd42002d1b12f216379780419e4b0d54575ca325e7981795beee9d" } } ], "extra": [ 1, 242, 21, 228, 64, 0, 5, 223, 154, 241, 144, 108, 247, 248, 118, 122, 131, 205, 88, 116, 200, 214, 199, 248, 164, 247, 99, 3, 197, 121, 196, 80, 115, 2, 17, 0, 0, 0, 12, 131, 104, 38, 109, 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