Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fda5c9943e8d699890a317f82102762ee169890166b09773fb14757f241d8ee

Tx prefix hash: a1de789543e18411c9d8ef24f48e4b9d9a87783e78046334c7c0f91b5e685d1c
Tx public key: 1a329f728fba1a2b5f9ee2bc99a5dfc66fea97acc66643b516f2c8c6d8ebf897
Timestamp: 1747642022 Timestamp [UCT]: 2025-05-19 08:07:02 Age [y:d:h:m:s]: 00:141:18:41:42
Block: 1286179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98971 RingCT/type: yes/0
Extra: 011a329f728fba1a2b5f9ee2bc99a5dfc66fea97acc66643b516f2c8c6d8ebf8970211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 146d7d6868f64f20bb5a739aee1813cb3a1d2fd6c187e3cf1e74b19122857da4 0.600000000000 1773644 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": 1286189, "vin": [ { "gen": { "height": 1286179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "146d7d6868f64f20bb5a739aee1813cb3a1d2fd6c187e3cf1e74b19122857da4" } } ], "extra": [ 1, 26, 50, 159, 114, 143, 186, 26, 43, 95, 158, 226, 188, 153, 165, 223, 198, 111, 234, 151, 172, 198, 102, 67, 181, 22, 242, 200, 198, 216, 235, 248, 151, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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