Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce06c5df3a3738a47ab1f7332c7272928f3e918f24deaf8b5a4f781f21b9af4

Tx prefix hash: 8664c1a760e26092c894a6b20981f17f4ef9693b3247cd22300e3fafa16ff622
Tx public key: 026a3c281344e46a6363b0a28534b214877567295f3f03f4ebbc34853404b534
Timestamp: 1717122842 Timestamp [UCT]: 2024-05-31 02:34:02 Age [y:d:h:m:s]: 00:347:23:01:49
Block: 1033702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248718 RingCT/type: yes/0
Extra: 01026a3c281344e46a6363b0a28534b214877567295f3f03f4ebbc34853404b53402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07efcdef33b7e222a6133a2b5685df2b22457a1a3a27ff49ea68ba1ed5aec733 0.600000000000 1502173 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": 1033712, "vin": [ { "gen": { "height": 1033702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07efcdef33b7e222a6133a2b5685df2b22457a1a3a27ff49ea68ba1ed5aec733" } } ], "extra": [ 1, 2, 106, 60, 40, 19, 68, 228, 106, 99, 99, 176, 162, 133, 52, 178, 20, 135, 117, 103, 41, 95, 63, 3, 244, 235, 188, 52, 133, 52, 4, 181, 52, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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